Please resolve this using the suggestion in the previous review. There is a reason the MAX entries are defined in the enum (also the reason why I made that suggestion).

Whilst it's unlikely the enum will change, if new entries are added then your code would be faulty and need updating. We would rather avoid that entirely (making less work for future contributors), which is why you compare to the MAX enum entry for such range checks.

done

Looks good now, thanks!